-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix/66 graceful crash handling #665
Conversation
420286e
to
08b5c7a
Compare
description: OCSP data related to requested the certificates | ||
type: object | ||
required: | ||
- hash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the ocsp_path optional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because if we have a chain of returned certificates, for example leaf<-subca2<-subca1, we agreed that a list of the same count of OCSP data will be returned, because matching the ocsp data to a certificate in everest-core will be very difficult, based on a certificate hash, because it is difficult to build that has, especially when intermediaries are involved. So, if a chain of 3 certificates is returned, then a vector of 3 ocsp data is returned, each matched to the certificate from the chain in order.
Some comments resolved, awaiting further feedback. |
c5d6f37
to
db49018
Compare
f4c0c59
to
72d1f8c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed for Bazel only. LGTM.
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
4229a94
to
5b2a238
Compare
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
@@ -146,10 +157,13 @@ cmds: | |||
description: Specifies the encoding of the key | |||
type: string | |||
$ref: /evse_security#/EncodingFormat | |||
include_ocsp: | |||
description: Specifies whether per-certificate OCSP data is also requested |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: Specifies whether per-certificate OCSP data is also requested | |
description: Specifies whether per-certificate OCSP data is also requested |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
When #665 was merged it did not point to git hashes on the main branch but on a now deleted feature branches
When #665 was merged it did not point to git hashes on the main branch but on a now deleted feature branches Signed-off-by: Kai-Uwe Hermann <[email protected]>
When #665 was merged it did not point to git hashes on the main branch but on a now deleted feature branches Signed-off-by: Kai-Uwe Hermann <[email protected]>
Describe your changes
Updated interface usage for CSR generation
Issue ticket number and link
EVerest/libocpp#604
EVerest/libevse-security#70
Checklist before requesting a review